Battery powered end point device for iot applications

ABSTRACT

Methods and systems of monitoring and managing a facility including a plurality of end point devices. One system includes an end point device including an electronic processor, the electronic processor powered by an energy source local to the end point device. The electronic processor is configured to receive data from at least one electro-mechanical element of a fixture associated with the facility, the data related to an operation of the fixture. The electronic processor is also configured to convert the data pursuant to a networking protocol. The electronic processor is also configured to enable, over a network associated with the networking protocol, transmission of the converted data for virtual processing.

RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent ApplicationNo. 63/057,116, filed on Jul. 27, 2020, the entire contents of which areincorporated herein by reference.

FIELD

Embodiments relate to monitoring and managing a facility having aplurality of end point devices, and, more particularly, to a smart andconnected modular battery powered end point device forinternet-of-things (“IoT”) applications.

SUMMARY

In the field of facility or building management, there is a desire tomonitor performance of restroom fixtures, such as, for example, faucets,flush valves, hand dryers, floor drains, air or room quality sensors,backflow preventers, bottle fillers, pressure sensors, leak detectionsensors, occupancy detection sensors, resource dispensers (for example,a soap dispenser, a sanitizer dispenser, a room deodorizer dispenser, apaper tower dispenser), and the like. As one example, a building managermay want to monitor water usage or consumption for one or more restroomfacilities within the building. Such monitoring may be performed forpredictive maintenance, alerting, for collecting data on usage of therestroom(s), or the like. For example, monitoring may indicate thatthere is a certain percentage of life remaining for a flush valve (or acomponent of the flush valve) based on a rated life of flushes and anumber of flush operations performed by the flush valve. As anotherexample, monitoring may generate alerts, such as a low soap alert, abackflow discharge in progress alert, a drain clogged alert, and thelike. However, these applications are typically in locations that arenot serviced by mains power, are difficult to reach, and are limited insize, which, ultimately, limits the size of batteries that may be used.Therefore, there is a need for a battery-powered solution that providesa low power consumption solution while also accommodating the limitedsize constraints.

Accordingly, the embodiments described herein provide methods andsystems for monitoring and managing a facility (e.g., a building or oneor more rooms within a building) using a plurality of smart andconnected modular battery powered end point devices. Embodimentsdescribed herein enable a quick and simple sensor input customizationwhile maintaining a common connectivity architecture to support datareporting to a central cloud-based database (for example, for variousIoT applications). Additionally, embodiments may be implemented withhardware and industrial designs engineered such that the assemblyprocess is easy, and, ultimately, makes the field serviceability of theproduct straight-forward. For example, the hardware electronics may bedesigned to intake various analog and digital inputs which provide theproduct great flexibility. Additionally, in some embodiments, thebattery life may be monitored using various indicators, such as agraphical representation of a fuel gauge. Alternatively or in addition,embodiments may generate alerts and warnings in response to detecting anend of battery life scenario, a battery replacement scenario, and thelike.

For example, one embodiment provides an end point device associated witha facility. The end point device includes a first energy source. The endpoint device also includes an electronic processor communicativelycoupled to the first energy source and powered by the first energysource. The electronic processor is configured to receive data from atleast one electro-mechanical element of a fixture associated with thefacility, the data related to an operation of the fixture. Theelectronic processor is also configured to convert the data pursuant toa networking protocol. The electronic processor is also configured toenable, over a network associated with the networking protocol,transmission of the converted data to a remote device for virtualprocessing.

Another embodiment provides a system for monitoring and managing afacility including a plurality of end point devices. The system includesan end point device including an electronic processor, the electronicprocessor powered by an energy source local to the end point device. Theelectronic processor is configured to receive data from at least oneelectro-mechanical element of a fixture associated with the facility,the data related to an operation of the fixture. The electronicprocessor is also configured to convert the data pursuant to anetworking protocol. The electronic processor is also configured toenable, over a network associated with the networking protocol,transmission of the converted data for virtual processing.

Yet another embodiment provides a method for monitoring and managing afacility. The method includes providing an end point device powered byan energy source, the energy source local to the end point device. Themethod also includes powering, with the energy source, one or morecomponents of the end point device. The method also includes receiving,with an electronic processor of the end point device, data from at leastone electro-mechanical elements of a fixture associated with thefacility, wherein the data is associated with an operation of thefixture. The method also includes, in response to receiving the data,converting, with the electronic processor, the data pursuant to anetworking protocol and transmitting, over a network associated with thenetworking protocol with the electronic processor, the converted datafor virtual processing.

Other aspects and embodiments will become apparent by consideration ofthe detailed description and accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 schematically illustrates a system for monitoring and managing afacility having a plurality of end point devices according to someembodiments.

FIG. 2 schematically illustrates an end point device included in thesystem of FIG. 1 according to some embodiments.

FIGS. 3A-3C illustrate an example electronics housing for an end pointdevice according to some embodiments.

FIGS. 4A-4C illustrate an example circuit diagram for electronics of anend point device according to some embodiments.

FIG. 5 schematically illustrates a facility device included in thesystem of FIG. 1 according to some embodiments.

FIG. 6 is a flowchart illustrating a method for monitoring and managinga facility having a plurality of end point devices using the system ofFIG. 1 according to some embodiments.

FIG. 7 schematically illustrates communication between components of thesystem of FIG. 1 according to some embodiments.

DETAILED DESCRIPTION

Before any embodiments are explained in detail, it is to be understoodthe embodiments are not limited in their application to the details ofconstruction and the arrangement of components set forth in thefollowing description or illustrated in the following drawings. Otherembodiments are possible and embodiments described and/or illustratedhere are capable of being practiced or of being carried out in variousways.

It should also be noted that a plurality of hardware and software-baseddevices, as well as a plurality of different structural components maybe used to implement the embodiments described herein. In addition,embodiments may include hardware, software, and electronic components ormodules that, for purposes of discussion, may be illustrated anddescribed as if the majority of the components were implemented solelyin hardware. However, one of ordinary skill in the art, and based on areading of this detailed description, would recognize that, in at leastone embodiment, the electronic based aspects of the embodiments may beimplemented in software (for example, stored on non-transitorycomputer-readable medium) executable by one or more processors. As such,it should be noted that a plurality of hardware and software-baseddevices, as well as a plurality of different structural components maybe utilized to implement various embodiments. It should also beunderstood that although certain drawings illustrate hardware andsoftware located within particular devices, these depictions are forillustrative purposes only. In some embodiments, the illustratedcomponents may be combined or divided into separate software, firmwareand/or hardware. For example, instead of being located within andperformed by a single electronic processor, logic and processing may bedistributed among multiple electronic processors. Regardless of how theyare combined or divided, hardware and software components may be locatedon the same computing device or may be distributed among differentcomputing devices connected by one or more networks or other suitablecommunication links.

FIG. 1 illustrates a system 100 for monitoring and managing a facility(e.g., a building or one or more rooms within a building) according tosome embodiments. In the illustrated example, the system 100 includes aplurality of end point devices 105 (collectively referred to herein as“the end point devices 105” and individually as “an end point device105”), a plurality of fixtures 107 (collectively referred to herein as“the fixtures 107” and individually as “a fixture 107”), a facilitydevice 110 (e.g., a gateway), a server 115 (e.g., cloud server), and auser device 120. In some embodiments, the system 100 includes fewer,additional, or different components than illustrated in FIG. 1 invarious configurations. For example, the system 100 may include multiplefacility devices 110, servers, 115, user devices 120, or a combinationthereof. Additionally, the system 100 may include any number of endpoint devices 105 and/or fixtures 107 and the two endpoint devices andfixtures illustrated in FIG. 1 are purely for illustrative purposes.Also, in some embodiments, one or more of the components of the system100 may be distributed among multiple devices, combined within a singledevice, or a combination thereof. As one example, in some embodiments,one or more of the end point devices 105 may be incorporated within afixture 107 as a single device. Accordingly, in some embodiments, thefunctionality described as being performed by the end point device 105(or a portion thereof) may be performed by a fixture 107 (includingbuilt-in or attached similar hardware and software components as the endpoint device 105).

The end point devices 105, the fixtures 107, the facility device 110,the server 115, and the user device 120 communicate over one or morewired or wireless communication networks 140. Portions of thecommunication networks 140 may be implemented using a wide area network(“WAN”), such as the Internet or a LoRa system, a local area network(“LAN”), such as a Bluetooth™ network or Wi-Fi, and combinations orderivatives thereof. Accordingly, components of the system 100 may beconfigured to communicate via Bluetooth, Wi-Fi, Zigbee, LTE/Cellular,wired ethernet, RS485/RS232, or the like. As one example, the end pointdevices 105 may communicate via LoRa with the facility device 110.Alternatively or in addition, in some embodiments, one or morecomponents of the system 100 communicate directly as compared to throughthe communication network 140. For example, in some embodiments, the endpoint devices 105 communicate directly with the facility device 110.Also, in some embodiments, the components of the system 100 communicatethrough one or more intermediary devices not illustrated in FIG. 1.

Additionally, in some embodiments, one or more components of the system100 communicate using LoRa or LoRaWAN networking protocols (for example,the end point device 105 and the facility device 110). Using suchnetworking protocols provides for secure, encrypted communication ofdata without use of a customer or building network. Accordingly, use ofsuch networking protocols may completely isolate an end point device 105(or other component of the system 100) from a customer or buildingnetwork.

A fixture 107 may include, for example, a faucet, a flushometer, a flushvalve, a soap dispenser, a handwashing system, a water service linemonitor, a backflow preventer, a floor drain, a hand dryer, a pressuresensor, a water use sensor, a flow sensor, a valve sensor, a lavatory, atoilet, a urinal, a water closet, a bottle and glass filler, a drain, adrinking water fountain, an air or room quality sensor (e.g., mayinclude a service request or product replenishment request button orother suitable activator), a backflow preventer, a leak detectionsensor, an occupancy detection sensor, and a resource dispenser (forexample, a soap dispenser, a sanitizer dispenser, a room deodorizerdispenser, a paper tower dispenser), and the like. Accordingly, in someembodiments, the fixture 107 provides a water management solution. Asseen in FIG. 1, each of the fixtures 107 is associated with one or moreelectro-mechanical (“EM”) elements 125. The EM elements 125 areconfigured to monitor and/or influence the operation of the fixture 107.An EM element 125 may include, but is not limited to, an actuator, aflow sensor, a position sensor, a proximity sensor, a thermocouple, andthe like. It is contemplated that the EM elements 125 may include anelectrical only element, a mechanical only element, or a combination ofan electrical and a mechanical element(s). The EM elements 125 mayinclude a single-piece component or multiple components.

As one example, in some embodiments, the fixture 107 is a faucet havinga sensor (for example, as a first EM element 125) configured to detectthe presence of a person within a specified zone. When the sensor istriggered (for example, by detecting the presence of a person), thesensor sends an “ON” signal to an actuator (as a second EM element 125)(for example, a valve actuating solenoid) thereby allowing water toselectively flow through the faucet. When the sensor is no longertriggered (for example, by detecting the absence of a person), thesensor sends an “OFF” signal to the actuator to stop water flow throughthe faucet. In some embodiments, the actuator is configured to maintainthe faucet in an open position for a predetermined period of time inresponse to receiving an “ON” signal. In such embodiments, thepredetermined period of time may be set by a user or facility entityvia, for example, the facility device 110, the user device 120, anothercomponent of the system 100, or a combination thereof.

As another example, in some embodiments, the fixture 107 is a flushvalve having a sensor (for example, as a first EM element 125)configured to detect the presence of a person within a specified zone.When the sensor is triggered (for example, by detecting the presence ofa person), the sensor sends an “ON” signal to the actuator (as a secondEM element 125) (for example, a valve actuating solenoid) to actuate avalve and initiate a flow of water for a flushing event. The flush valvewill then remain open for a predetermined period of time (for example, 5seconds, 10 seconds, and the like) at least partially dependent upon anoperating parameter set by the user via, for example, the facilitydevice 110, the user device 120, another component of the system 100, ora combination thereof.

As yet another example, in some embodiments, the fixture 107 is aresource dispenser (such as a soap dispenser, a hand towel dispenser,and the like) having a sensor (for example, as a first EM element 125)configured to detect the presence of a person within a specified zone.When the sensor is triggered (for example, by the hands of a person),the sensor sends an “ON” signal to an actuator (for example, as a secondEM element 125) to trigger a resource dispensing event (for example,actuation of a gear, a valve, or solenoid, and the like to initiatedispensing of a resource). The resource dispenser is configured to allowa predetermined volume or amount of a resource to be dispensed for eachactivation. In such embodiments, the volume or amount or timing of aresource to be dispensed may be set and adjusted by the user via, forexample, the facility device 110, the user device 120, another componentof the system 100, or a combination thereof.

The resource dispenser may also include a second sensor (for example, asa third EM element 125) to monitor the level or amount of resourceremaining in a reservoir or receptacle. In some embodiments, the secondsensor detects a current level or amount of resource in the reservoir orreceptacle at a given moment in time. Alternatively or in addition, thesecond sensor may detect when the resource falls below a predeterminedamount or level.

As yet another example, in some embodiments, the fixture 107 is a waterservice line monitor. The water service line monitor includes a sensor(for example, as a first EM element 125) configured to be retrofit ontoan existing water service line and is configured to monitor theflow-rate of water therethrough, the presence of a backflow event, or acombination thereof. More specifically, the sensor may be configured todetect a flow rate, a presence of a backflow event, and the like.

As seen in FIG. 1, an end point device 105 generally includes acommunication link with at least one fixture 107. The end point devices105 may span multiple facilities, locations, rooms, and the like. Insome embodiments, each of the end point devices 105 is associated with(located within) the same facility (for example, a restroom facility).However, in other embodiments, the end point devices 105 are associatedwith multiple facilities. As one example, a first end point device maybe associated with a first facility, and a second end point device maybe associated with a second different facility that is either in thesame building as the first facility or in an entirely differentbuilding. Alternatively or in addition, in some embodiments, each of theend point devices 105 is associated with the same type of restroomfixture (for example, the fixture 107). However, in other embodiments,the end point devices 105 are associated with multiple different typesof restroom fixtures (for example, the fixture 107). As one example, afirst end point device may be associated with a faucet (as a firstfixture 107) and a second end point device may be associated with a soapdispenser (as a second fixture 107).

FIG. 2 illustrates an end point device 105 according to someembodiments. In the illustrated example, the end point device 105includes an electronic processor 200, a memory 205, a communicationinterface 210, and an energy source 220. The electronic processor 200,the memory 205, the communication interface 210, and the energy source220 communicate wirelessly, over one or more communication lines orbuses, or a combination thereof. In some embodiments, one or morecomponents of the end point device 105 may be distributed among multipledevices, integrated into a single device, or a combination thereof. Insome embodiments, the end point device 105 may perform additionalfunctionality other than the functionality described herein. In someembodiments, the end point device 105 may include additional, different,or fewer components than those illustrated in FIG. 2 in variousconfigurations. As one example, in some embodiments, the end pointdevice 105 includes multiple energy sources 220. As another example, insome embodiments, the end point device 105 includes one or moreexpansion ports allowing for future expansion of the end point device105. As one example, additional electro-mechanical (EM) elements of afixture 107 may be connected to the end point device 105 via the one ormore of the expansion ports.

The communication interface 210 allows the end point device 105 tocommunicate with devices external to the end point device 105. Forexample, as illustrated in FIG. 1, the end point device 105 maycommunicate with the fixture 107 (or an EM element 125 thereof), thefacility device 110, the server 115, the user device 120, or acombination thereof through the communication interface 210. Thecommunication interface 210 may include a port for receiving a wiredconnection to an external device (for example, a universal serial bus(“USB”) cable and the like), a transceiver for establishing a wirelessconnection to an external device (for example, over one or morecommunication networks 140, such as the Internet, LAN, a WAN, such as aLoRa network or system, and the like), or a combination thereof. As oneexample, in some embodiments, the communication interface 210 includes aport for receiving a wired connection between the facility device 110and an EM element 125 of a corresponding fixture 107. As anotherexample, in some embodiments, the communication interface 210 includes aradio or transceiver for establishing a wireless connection, over a LoRasystem or network, between the end point device 105 and the facilitydevice 110.

The electronic processor 200 includes a microprocessor, anapplication-specific integrated circuit (“ASIC”), or another suitableelectronic device for processing data, and the memory 205 includes anon-transitory, computer-readable storage medium. The electronicprocessor 200 is configured to access and execute computer-readableinstructions (“software”) stored in the memory 205. The software mayinclude firmware, one or more applications, program data, filters,rules, one or more program modules, and other executable instructions.For example, the software may include instructions and associated datafor performing a set of functions, including the methods describedherein. For example, in some embodiments, the electronic processor 200is configured to enable management and/or monitoring of the operation ofthe corresponding fixture 107 either directly or indirectly (forexample, via the EM element(s) 125 of the corresponding fixture 107). Insome embodiments, the electronic processor 200 enables management and/ormonitoring of the operation of a corresponding fixture 107 by receivingfixture data from the fixtures 107, converting the fixture data fortransmission, and enabling transmission of the converted data to, forexample, the facility device 110, the server 115, the user device 120,another component of the system 100, or a combination thereof.

Accordingly, in some embodiments, the electronic processor 200 isconfigured to interact with and collect data regarding an operation of afixture 107 (as fixture data) via the EM elements 215 either directly orindirectly. In some embodiments, the end point device 105 is configuredto remain in a sleep mode (or deep sleep mode) until an action oroperation is detected with respect to a fixture 107 associated with theend point device 105 (for example, detecting the presence of a user). Inresponse to detecting the action or operation, the end point device 105may then wake-up to receive fixture data, convert the fixture data fortransmission, and transmit the fixture data (in a minimum powerconsumption mode) to, for example, the facility device 110, the server115, the user device 120, another component of the system 100, or acombination thereof. This results in optimized battery life for theproduct. As one example, in some embodiments, when the end point device105 transmits the converted fixture data (for example, as one or moredata packets) to the facility device 110, the transmission may occurthrough adaptable data rate, which automatically selects the most easilyavailable channel such that the right channel does not have to besearched for, which further aids in the optimization of power.

As seen in FIG. 2, the end point device 105 also includes the energysource 220. The energy source 220 powers one or more components of theend point device 105, such as the electronic processor 200. The energysource 220 may be a battery, such as an energy efficient battery, are-chargeable battery, a lithium-ion battery, a replaceable battery, orthe like. As one example, the energy source 220 is a standard battery(for example, AAA, AA, C, D sized batteries). As noted above, in someembodiments, the end point device 105 includes multiple energy sources220 (for example, a first energy source, a second energy source, and thelike). In such embodiments, the multiple energy sources 220 may be ofthe same type, different types, or a combination thereof. As oneexample, the end point device 105 may include three AA batteries as theenergy sources 220.

In some embodiments, one or more components of the system 100 mayalready be present in a completed fixture 107 (for example, a proximitysensor and an actuator in an automated faucet). In such embodiments,additional components may be retro-fit onto the existing fixture 107.Accordingly, in some embodiments, the end point device 105 (orcomponents thereof) may be retro-fit onto or into the existing fixture107. As one example, a transmitter, a receiver, a transceiver, or acombination thereof (as part of the communication interface 210), theelectronic processor 200, the energy source 220, or a combinationthereof may be mounted in the plumbing immediately upstream of aparticular fixture 107. In other examples, the retro-fit may includeupdating firmware in the already existing device. In still otherexamples, the retro-fit may include integrating elements into apreviously existing fixture 107.

FIGS. 3A-3C illustrate an example electronics housing 305 for an endpoint device 105 according to some embodiments. As seen in FIGS. 3A-3C,the end point device 105 may include one or more wires or cables 310extending from the housing 305. The wires 310 may provide a direct orindirect wired connection to, for example, one or more of the EMelements 125 of a fixture 107 associated with the end point device 105.As seen in FIGS. 3B-3C, the housing 305 includes a battery holder 315(for example, an energy source holder) for receiving one or morebatteries (for example, as the energy sources 220). As seen in FIG. 3B,the housing 305 may include a lid portion 307. The lid portion 307allows a user to easily access the components enclosed within thehousing 305 (for example, to remove and replace one or more of theenergy sources 220). FIGS. 3B-3C also illustrates a circuit board 320enclosed within the housing 305 (for example, one or more electronicalcomponents of the end point device 105, such as the electronic processor200).

FIGS. 4A-4C illustrate an example circuit diagram 400 for the circuitboard 320 of the end point device 105 according to some embodiments. Asnoted above, in some embodiments, one or more components of the system100 may be retro-fit onto or into an existing fixture 107. Accordingly,in some embodiments, the electronics housing 305 (and the componentstherein) may be retro-fit to an existing fixture 107. As one example,the end point device 105 may be mounted to a fixture 107 andcommunicatively connect the fixture 107 to the end point device 105 (forexample, by connecting EM elements 125 of the fixture 107 to the endpoint device 105 directly or indirectly via one or more of the wires orcables 310). Accordingly, in some embodiments, one or more components ofthe end point device 105 (such as the electronics housing 305, includingthe components therein) are designed as discrete, self-enclosed, add-oncomponents or devices capable of retro-fitting to an existinginstallation of a fixture 107.

FIG. 5 illustrates the facility device 110 according to someembodiments. In the illustrated example, the facility device 110includes a facility electronic processor 500, a facility memory 505, anda facility communication interface 510. The facility electronicprocessor 500, the facility memory 505, and the facility communicationinterface 510 communicate wirelessly, over one or more communicationlines or buses, or a combination thereof. The facility device 110 mayinclude additional, different, or fewer components than thoseillustrated in FIG. 5 in various configurations. For example, in someembodiments, the facility device 110 includes a human-machine interfacefor interacting with a user. The human machine interface may include oneor more input devices, one or more output devices, or a combinationthereof. In some embodiments, one or more components of the facilitydevice 110 may be distributed among multiple devices, integrated into asingle device, or a combination thereof. In some embodiments, thefacility device 110 may perform additional functionality other than thefunctionality described herein. Also, the functionality (or a portionthereof) described herein as being performed by the facility device 110may be distributed among multiple devices.

The facility communication interface 510 allows the facility device 110to communicate with devices external to the facility device 110. Forexample, as illustrated in FIG. 1, the facility device 110 maycommunicate with the end point devices 105, the fixtures 107, the server115, the user device 120, or a combination thereof through the facilitycommunication interface 510. The facility communication interface 510may include a port for receiving a wired connection to an externaldevice (for example, a USB cable and the like), a transceiver forestablishing a wireless connection to an external device (for example,over one or more communication networks 140, such as the Internet, aLAN, a WAN, such as a LoRa system, and the like), or a combinationthereof.

The facility electronic processor 500 is configured to access andexecute computer-readable instructions (“software”) stored in thefacility memory 505. The software may include firmware, one or moreapplications, program data, filters, rules, one or more program modules,and other executable instructions. For example, the software may includeinstructions and associated data for performing a set of functions,including the methods described herein.

In some embodiments, the facility device 110 serves as a gateway orintermediary device that receives data (for example, the fixture data)from the electronic processors 200 of one or more of the end pointdevices 105 and forwards the collected data to another component forprocessing, such as the server 115, the user device 120, or acombination thereof. For example, in some embodiments, the facilitydevice 110 forwards the data to a remote server (for example, the server115) for virtual processing. Accordingly, as noted above, in someembodiments, the functionality (or a portion thereof) described as beingperformed by the facility device 110 may be performed by another remotedevice or server (not shown).

Returning to FIG. 1, the server 115 and the user device 120 arecomputing devices, such as a desktop computer, a laptop computer, atablet computer, a terminal, a smart telephone, a smart television, asmart wearable, or another suitable computing device that interfaceswith a user. Although not illustrated in FIG. 1, the server 115 and theuser device 120 may include similar components as the facility device110, such as an electronic processor (for example, a microprocessor, anASIC, or another suitable electronic device), a memory (for example, anon-transitory, computer-readable storage medium), a communicationinterface, such as a transceiver, for communicating over thecommunication network 140 and, optionally, one or more additionalcommunication networks or connections, and one or more human machineinterfaces.

In some embodiments, the server 115 may include multiple electronicprocessors, multiple memory modules, multiple communication interfaces,or a combination thereof. Also, it should be understood that thefunctionality described herein as being performed by the server 115 maybe performed in a distributed nature by a plurality of computers locatedin various geographic locations. For example, the functionalitydescribed herein as being performed by the server 115 may be performedby a plurality of computers included in a cloud computing environment.

The server 115 is configured to monitor and manage one or morefacilities (e.g., individual restrooms or entire buildings), includingthe fixtures 107 therein. In some embodiments, the server 115 (via anelectronic processor of the server 115) may receive fixture data fromthe facility device 110. In response to receiving the fixture data, theserver 115 may process the fixture data in order to determine usageinformation or patterns associated with the one or more facilities,including the fixtures 107 thereof. The server 115 may store the usageinformation or patterns in, for example, a memory of the server 115.Alternatively or in addition, the server 115 may transmit the usageinformation or patterns to a remote device for storage.

A user may interact with and access data associated with one or morefacilities, such as one or more of the fixtures 107 therein (forexample, the usage information or patterns determined by the server115). The user device 120 may be used by an end user, such as a facilityentity, to monitor and manage a facility (a single restroom or multiplerestrooms in a building), one or more fixtures 107 of a facility, or acombination thereof. For example, a user may access and interact withthe data determined by the server 115 to view and understand usagepatterns, which may allow a facility entity or maintainer insights into,for example, how to optimize cleaning and maintenance schedules, whetherthere is a need for additional facilities, end point devices, or acombination thereof. For example, to communicate with the server 115(i.e., the usage information or patterns determined by the server 115),the user device 120 may store a browser application or a dedicatedsoftware application executable by an electronic processor forinteracting with the server 115.

FIG. 6 is a flowchart illustrating a method 600 for monitoring andmanaging a facility according to some embodiments. The method 600 willbe described with reference to FIG. 7. FIG. 7 schematically illustratescommunication between components of the system 100 according to someembodiments.

As seen in FIG. 6, the method 600 includes providing an end point device105 powered by the energy source 220 (at block 605). Accordingly, insome embodiments, the energy source 220 is local to the end point device105. As noted above, in some embodiments, the end point device 105 isprovided or mounted to a wall in a facility or to a pre-existinginstallation of a fixture 107. However, in other embodiments, the endpoint device 105 is provided to or mounted to the fixture 107 prior toor during installation of the fixture 107 within a facility. As oneexample, the electronic housing 305 of FIGS. 3A-3C are provided ormounted to a wall in a facility or to the fixture 107.

The energy source 220 then powers one or more components of the endpoint device 105 (at block 610). For example, the energy source 220 maypower the electronic processor 200. In some embodiments, the electronicprocessor 20 receives data (for example, the fixture data) from at leastone EM element 125 (a first EM element) included in a set of EM elements125 (at block 615). The data received from the first EM element 125 maybe associated with an operation of the fixture 107. For example, asillustrated in FIG. 7, the fixtures 107 (the EM elements 125 thereof)transmit fixture data to the end point devices 105.

In some embodiments, in response to receiving the data (at block 615),the electronic processor 200 converts the data pursuant to a networkingprotocol (at block 620). In some embodiments, the electronic processor200 may convert the data pursuant to specific networking protocolconsistent with a network connection between the end point device 105and the facility device 110. As one example, the electronic processor200 may convert the data pursuant to LoRa networking protocols fortransmission over a LoRa connection between the end point device 105 andthe facility device 110.

In some embodiments, the electronic processor 200 also transmits thedata for remote or virtual processing (at block 625). In someembodiments, the electronic processor 200 transmits the converted datafor virtual processing over a network associated with the networkingprotocol. As described above, the electronic processor 200 may transmitthe data to the facility device 110 (as a gateway device). For example,as illustrated in FIG. 7, the end point devices 105 transmit theconverted fixture data to the facility device 110. In some embodiments,the end point device 105 (for example, the electronic processor 200)maintains a backlog of data packets (for example, the converted data)until a connection to, for example, the facility device 110 is available(for example, in the event that a connection to the facility device 110is temporarily unavailable). The facility device 110 may then forwardthe data to a remote device, server, or database for virtual processingin the cloud, such as, for example, the server 115, the user device 120,or a combination thereof (as seen in FIG. 7). As one example, a user mayuse the user device 120 (or another remote device) to access andinteract with the data. The user may view and interact with usagepatterns, which may allow a facility entity or maintainer insights into,for example, how to optimize cleaning and maintenance schedules (forexample, for preventative or predicted maintenance), whether there is aneed for additional facilities, end point devices, or a combinationthereof, and the like. As noted above, in some embodiments, the server115 is configured to monitoring and managing one or more facilities,including the fixtures 107 therein. In some embodiments, the server 115(via an electronic processor of the server 115) may receive fixture datafrom the facility device 110. In response to receiving the fixture data,the server 115 may process the fixture data in order to determine usageinformation or patterns associated with the one or more facilities,including the fixtures 107 thereof. Alternatively or in addition, insome embodiments, the server 115 may monitor or track a battery or powerlevel (for example, as a battery condition or characteristic) associatedwith the end point device 105.

As one example, where the fixture 107 is a faucet, the server 115 mayanalyze the fixture data to monitor the communications between the EMelements 125 of a fixture 107 (for example, a sensor and an actuator) totrack, among other things, the number of “ON” and “OFF” signals (oractivations). Alternatively or in addition, the server 115 may analyzethe fixture data to detect the flow of water by monitoring temperaturedata from a temperature sensor (as an EM element 125 of the fixture 107)either positioned within the drain or the faucet itself. Alternativelyor in addition, the server 115 may analyze the fixture data to determinewhen a run-on condition has occurred in response to determine that apredetermined period of time set by a user is exceeded and the faucetdid not return to an “OFF” condition or water flow is still detected.Alternatively or in addition, the server 115 may analyze the fixturedata to calculate water usage indirectly based at least in part on aduration of time that the valve of the faucet remains open and anestimated water flow rate.

As yet another example, where the fixture 107 is a flush valve, theserver 115 may analyze the fixture data to monitor a magnitude of avoltage and/or current supplied to the EM element 125 (for example, anactuator) of the fixture 107 to track when a flushing event has beeninitiated. Alternatively or in addition, the server 115 may analyze thefixture data to determine when an “ON” signal is provided (for example,a person is detected) but no corresponding movement of the valve occurs.In such instances, the server 115 may generate and provide an errorsignal such that an alert may be generated via, for example, thefacility device 110, the user device 120, another component of thesystem 100, or a combination thereof. Such faults may be detected bydetecting an elevated voltage or current rate (for example, motor isbound). Alternatively or in addition, the server 115 may analyze thefixture data to determine a length of time a person is detected usingthe fixture 107 on any given instance.

As yet another example, where the fixture 107 is a resource dispenser,the server 115 may analyze the fixture data to monitor a magnitude of avoltage and/or current supplied to an EM element 125 (for example, anactuator) of a fixture 107 to track when a resource dispensing event hasoccurred. Alternatively or in addition, the server 115 may analyze thefixture data to monitor a level or amount of resource remaining in areservoir of the fixture 107. The server 115 may calculate an amount ofresource remaining in a reservoir of the fixture 107 by subtracting apredetermined volume or amount of resource discharged during a resourcedispensing event for each detected activation. In some embodiments, whenthe server 115 determines that a level or amount of resource remainingin a reservoir of the fixture 107 has fallen below a predeterminedamount or level, the server 115 may generate and provide an error signalsuch that an alert may be generated via, for example, the facilitydevice 110, the user device 120, another component of the system 100, ora combination thereof.

Additionally, in some embodiments, the battery life (for example, anenergy level or energy usage) may be monitored using various indicators,such as a graphical representation of a fuel gauge. Alternatively or inaddition, in some embodiments, the server 115 (an electronic processorthereof) may generate alerts and warnings in response to detecting apredetermined energy level, where the predetermined energy levelindicates an end of battery life scenario, an energy source replacementscenario, and the like. As one example, when the electronic processor ofthe server 115 detects a predetermined energy level indicating a lowenergy level, the electronic processor of the server 115 may generateand transmit a low energy level alert to a user of the user device 120(via, for example, a display device of the user device 120).

Thus, the embodiments provide, among other things, to methods andsystems for monitoring and managing a facility having a plurality of endpoint device. Various features and advantages of certain embodiments areset forth in the following claims.

What is claimed is:
 1. An end point device associated with a facility,the end point device comprising: a first energy source; and anelectronic processor communicatively coupled to the first energy sourceand powered by the first energy source, the electronic processorconfigured to receive data from at least one electro-mechanical elementof a fixture associated with the facility, the data related to anoperation of the fixture, and convert the data pursuant to a networkingprotocol, and enable, over a network associated with the networkingprotocol, transmission of the converted data to a remote device forvirtual processing.
 2. The end point device of claim 1, wherein thenetworking protocol is a LoRa networking protocol.
 3. The end pointdevice of claim 1, wherein the fixture is a water management solution.4. The end point device of claim 1, wherein the electronic processor isconfigured to transmit the data for virtual processing via a gatewaydevice of the facility.
 5. The end point device of claim 1, wherein theend point device is associated with the fixture.
 6. The end point deviceof claim 1, wherein the end point device includes a second energysource, the second energy source configured to power the electronicprocessor.
 7. The end point device of claim 1, wherein the end pointdevice includes an energy source holder for receiving the first energysource.
 8. The end point device of claim 7, wherein the energy sourceholder and the first energy source are positioned within a housinghaving a lid portion.
 9. The end point device of claim 8, wherein thelid portion is configured to enable access to the energy source holderand the first energy source.
 10. The end point device of claim 1,wherein the first energy source is a replaceable battery.
 11. A systemfor monitoring and managing a facility including a plurality of endpoint devices, the system including: an end point device including anelectronic processor, the electronic processor powered by an energysource local to the end point device, wherein the electronic processoris configured to receive data from at least one electro-mechanicalelement of a fixture associated with the facility, the data related toan operation of the fixture, and convert the data pursuant to anetworking protocol, and enable, over a network associated with thenetworking protocol, transmission of the converted data for virtualprocessing.
 12. The system of claim 11, further comprising: a facilitydevice associated with the facility.
 13. The system of claim 12, whereinthe electronic processor is configured to transmit the converted data tothe facility device, the facility device configured to forward theconverted data to a remote device for virtual processing.
 14. The systemof claim 13, wherein the remote device is a central cloud-baseddatabase.
 15. The system of claim 11, wherein the networking protocol isa LoRa networking protocol.
 16. The system of claim 11, wherein thevirtual processing includes monitoring an energy level of the energysource local to the end point device and, in response to detecting apredetermined energy level, generating a low energy level alert.
 17. Thesystem of claim 11, wherein the virtual processing includes monitoringan energy level of the energy source local to the end point device andgenerating a graphical indicator of the energy level.
 18. A method formonitoring and managing a facility, the method comprising: providing anend point device powered by an energy source, the energy source local tothe end point device; powering, with the energy source, one or morecomponents of the end point device; receiving, with an electronicprocessor of the end point device, data from at least oneelectro-mechanical elements of a fixture associated with the facility,wherein the data is associated with an operation of the fixture; and inresponse to receiving the data, converting, with the electronicprocessor, the data pursuant to a networking protocol, and transmitting,over a network associated with the networking protocol with theelectronic processor, the converted data for virtual processing.
 19. Themethod of claim 18, further comprising: mounting the end point device tothe fixture; and communicatively coupling the end point device to thefixture, wherein the fixture is a pre-existing fixture of the facility.20. The method of claim 18, wherein transmitting the converted data forvirtual processing includes transmitting the converted data to afacility device, the facility device configured to collect dataassociated with a facility and forward the data associated with thefacility to a remote device for virtual processing.